4.1. Events
The following set of tests verifies that basic events can be passed back and forth between the mobile device and the server. They also attempt to verify the following:
that events with large amounts of data do not adversely affect the mobile device.
that any form of truncation that may need to occur on the device does not adversely effect the representation on the server
that reminders can be part of the event
that appropriate mappings are done for access level and priorities
that special characters and multi-byte characters can be correctly displayed on either side.
Test ID | Objective | Procedure | Expected Result |
|---|---|---|---|
1.1 Create an Event with a Reminder | Verify that basic events synchronize to the device. Verify that filling out all fields with long strings does not cause the device issues Verify that reminders can be sent | From the Server, create a simple future event, filling out all fields with maximum input, with a reminder. Perform a synchronization From the device, modify the event and remove the reminder. Perform a synchronization | The event should display on the device with all fields on the server correctly mapped to corresponding fields on the device. The device can only display what it supports and perhaps may need to truncate certain fields but the user should see an accurate representation of the event. The reminder should also be set on the device. After making modifications and synchronizing, the changes should display on the server as well. There should be no evidence of any truncation server-side if truncation occurred client-side but the field itself was not actually part of the modification done. |
1.2 Access Level and Priority | Verify that access level and priority values in events correctly synchronize to the device. Verify that any form of mapping that occurs does not have adverse effects | From the Server, create an event with default access and priority (e.g. Normal/Medium). Perform a synchronization From the device, modify the event. Perform a synchronization Repeat making sure to test all supported access level and priorities. | The event should display on the device with the access level and priority appropriately mapped if needed. After making modifications and synchronizing, the changes should display on the server as well. There should be no evidence of any change server-side to the access level or priority if not actually part of the modification done |
1.3 Special Characters From Server | Verify that special characters in events correctly synchronize to the device. | From the Server, create an event filling out all fields with special characters. Perform a synchronization From the device, modify the event. Perform a synchronization | The event should display on the device with all fields on the server correctly mapped to corresponding fields on the device. All special characters should correctly display on the device as it is displayed on the server. After modifying the event, the characters should remain correctly displayed on both the device and server and the changes made on the device should be reflected on the server |
1.4 Multi-Byte Characters From Server | Verify that multi-byte characters in events correctly synchronize to the device. | From the server, create a meeting filling out all fields with multi-byte characters. Perform a synchronization From the device modify the event. Perform a synchronization | The event should display on the device with all multi-byte characters correctly displayed. After modifying the event, the multi-byte characters should remain correctly displayed on both the device and server, and the changes made on the device should be reflected on the server. |
1.5 Deletion | Verify that events deleted server side are deleted on the device | From the server delete all events created in previous tests. Perform a synchronization | The deleted events should not be displayed on the device |
Test ID | Objective | Procedure | Expected Result |
|---|---|---|---|
1.6 Create an Event with a Reminder | Verify that basic events synchronize to the server. Verify that reminders can be sent | From the device, create a simple future event with a reminder. Perform a synchronization From the server, edit the event and remove the reminder. Perform a synchronization | The event should display on the server with all fields mapped correctly. The reminder should be set on the server as well. After editing the meeting and syncing, the meeting should be updated on the device. |
1.7 Access Level and Priority (can only be done if device supports setting an access level or priority) | Verify that access level and priority values in events correctly synchronize to the server. | From the device, create an event with default access and priority (e.g. Normal/Medium). Perform a synchronization Repeat making sure to test all supported access level and priorities. | The event should display on the server with the access level and priority appropriately mapped if needed. |
1.8 Special Characters from Device | Verify that special characters in events correctly synchronize to the server. | From the device, create an event filling out all fields with special characters. Perform a synchronization From the server, modify the event. Perform a synchronization | The event should display on the server with all fields on the device correctly mapped to corresponding fields on the server. All special characters should correctly display on the server as it is displayed on the device. After modifying the event, the characters should remain correctly displayed on both the device and server. |
1.9 Multi-Byte Characters from Device | Verify that multi-byte characters in meetings correctly synchronize to the server. | From the device, create a meeting filling out all fields with multi-byte characters. Perform a synchronization From the server, modify the event Perform a synchronization | The event should display on the server with all fields on the device correctly mapped to corresponding fields on the server. All multi-byte character should be displayed correctly. After modifying the event, the multi-byte characters should remain correctly displayed on both the device and server, and the changes on the server should be reflected on the device. |
1.10 Deletion | Verify that events deleted device side are deleted on the server | From the device delete all events created in previous tests. Perform a synchronization | The deleted events should be deleted off of the server as well. |